ࡱ> M kObjbj== "WWkKl        ''''d' sj( +++++J--H$݌ h .++..;  ++-;;;.z + +;.;>;<.H  +t( @jt8& d"'66@LC0sv0e;e;      eHealth 5.5 Cloning Procedure Cloning eHealth 5.5 can be an effective means of doing a dry run of the eHealth 5.5 to 5.6 upgrade procedure. Outline of Steps  TOC \o "1-2" \h \z  HYPERLINK \l "_Toc32147732" 1 Find and Resolve Problems with UNIX Groups  PAGEREF _Toc32147732 \h 2  HYPERLINK \l "_Toc32147733" 1.1 Determine if you have Group Problems  PAGEREF _Toc32147733 \h 2  HYPERLINK \l "_Toc32147734" 1.2 Identify the Target dba Group  PAGEREF _Toc32147734 \h 5  HYPERLINK \l "_Toc32147735" 1.3 Create Local Password and Group Entries If Needed  PAGEREF _Toc32147735 \h 5  HYPERLINK \l "_Toc32147736" 1.4 Homogenize the Groups  PAGEREF _Toc32147736 \h 5  HYPERLINK \l "_Toc32147737" 1.5 Re-run the nhCheckOracleGroup Command  PAGEREF _Toc32147737 \h 6  HYPERLINK \l "_Toc32147738" 1.6 Issue a Recursive Chgrp in NH_HOME  PAGEREF _Toc32147738 \h 7  HYPERLINK \l "_Toc32147739" 1.7 Restart eHealth 5.5 and Oracle 8i  PAGEREF _Toc32147739 \h 7  HYPERLINK \l "_Toc32147740" 2 Validate that eHealth 5.5 is Working Properly  PAGEREF _Toc32147740 \h 8  HYPERLINK \l "_Toc32147741" 2.1 Make Sure eHealth 5.5 is Polling  PAGEREF _Toc32147741 \h 8  HYPERLINK \l "_Toc32147742" 2.2 Validate that you can Bring the System Down and Up  PAGEREF _Toc32147742 \h 8  HYPERLINK \l "_Toc32147743" 3 Backup your eHealth 5.5 system.  PAGEREF _Toc32147743 \h 9  HYPERLINK \l "_Toc32147744" 4 Install eHealth 5.6 and bring system to Transition Mode.  PAGEREF _Toc32147744 \h 10  HYPERLINK \l "_Toc32147745" 5 Validate that Transition Mode is functioning properly.  PAGEREF _Toc32147745 \h 11  HYPERLINK \l "_Toc32147746" 6 SOMETHINGize the system by upgrading Oracle 8i to Oracle 9i.  PAGEREF _Toc32147746 \h 12  No Way to Cut Over Without Data Loss We thought it would be important to mention that it is not possible to move your production eHealth 5.5 system to a new system running eHealth 5.6 without incurring data loss (from pollers). So you cannot use this cloning procedure to accomplish this. Validate The Second System These steps are written with the assumption that you are cloning your production system in an effort to test the upgrade procedure. If you are cloning your production system to test the effectiveness and performance of new hardware (or system configuration changes), then you can obviously make appropriate adjustments to these steps. The second system can have: Its own IP address Its own Hostname The second system should have: Exact same operating system Exact same operating system patches Exact same physical and virtual (SWAP) memory Same network access to the elements being polled Same physical disk layout and at least as much disk space on each partition Additionally, for UNIX: Exact same /etc/passwd file Exact same /etc/shadow file (if appropriate) Exact same /etc/group file Exact same /etc/nsswitch.conf file Exact same /etc/passwd file with UNIX groups that did not affect Oracle 8i, but which cause problems for Oracle 9i (and thus eHealth 5.6): Become root on your eHealth 5.5 system: su root Run the nhCheckOracleGroup utility. To get this utility contact your Concord Beta Buddy: nhCheckOracleGroup Normal output looks something like this: Looking for unix group problems that break Oracle 9i/eHealth 5.6 ... :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :: eHealth NH_USER = nhuser :: NH_USER's unix group = dba :: All NH_USER's groups = dba :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :: inst_group (/var/opt) = dba :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :: 8.1.7 ORACLE_HOME = /export/pipe1/oracle/oracle.8.1.7 :: ORACLE config.c group = :: ORACLE config.s group = dba :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :: 8.1.7 OWNER = oracle :: ORACLE's unix group = dba :: All ORACLE's groups = dba :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: done (no problems detected). Error output looks something like this: :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :: eHealth NH_USER = nhuser :: NH_USER's unix group = admin :: All NH_USER's groups = admin :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :: inst_group (/var/opt) = dba :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :: 8.1.7 ORACLE_HOME = /export/pipe1/oracle/oracle.8.1.7 :: ORACLE config.c group = :: ORACLE config.s group = dba ( this group is needed for Step  REF _Ref32144764 \w \h 1.2 :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: :: 8.1.7 OWNER = oracle :: ORACLE's unix group = dba :: All ORACLE's groups = dba :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: +-----------------------------------------------------------------------------+ | PROBLEMS WITH UNIX GROUP MAY BREAK ORACLE 9i | | - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - | | COG-00002: EXE config group does not match ORACLE OWNER's unix group | | - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - | | (details omitted) +-----------------------------------------------------------------------------+ There are several distinct errors concerning UNIX groups. Your system may have more than one of these conditions. None of these conditions can exist before proceeding, or your system may be unusable and you will need to resort to backups and start the upgrade process all over. Most eHealth 5.5 customers will experience COG-00001 (it will be unusual if you do not) and the others are more rare. Unfortunately, the rarer conditions are resolved more easily, while COG-00001 requires some tedious work. COG-00001: primary unix groups of NH_USER and ORACLE OWNER do not match Likelihood:You are almost guaranteed to encounter this problem.Cause:A new restriction in eHealth 5.6 brought about by our upgrade to Oracle 9iResolution:You must carefully follow the rest of the steps in this section. This may take a few hours. COG-00002: EXE config group does not match ORACLE OWNER's unix group Likelihood:Rare.Cause:Can be caused by a system administrator who has chgrped $ORACLE_HOME, or by a system administrator changing the passwd entry for the oracle account after the Oracle software has been installed.Resolution:You must recursively chgrp $ORACLE_HOME back to the UNIX group that the Oracle installer compiled and linked into the Oracle executables: Determine the dba group that is embedded into the Oracle kernel by following the next step:  REF _Ref32144764 \r \h  \* MERGEFORMAT 1.2  REF _Ref32144764 \h  \* MERGEFORMAT Identify the Target dba Group . Perform a recursive chgrp in $ORACLE_HOME: su root cd /opt/ehealth chgrp R dbagroupid . (where dbagroupid is the numeric group ID corresponding to the dba group) COG-00003: Oracle source code is out of synch Likelihood:Extremely Rare.Cause:Probably caused by multiple attempts to install Oracle 8.1.7 as different UNIX users (or the same user with different passwd entries), without completely cleaning the system in between.Resolution:You may need to rebuild some Oracle executables or (worst case) re-install Oracle 8.1.7. This is so unlikely to occur that if you encounter this error, you should immediately contact your Concord Beta Buddy and ask that the problem be escalated to our database engineering team. COG-00004: unix group in Oracle inventory does not match ORACLE OWNER's Likelihood:Somewhat common.Cause:Caused by multiple attempts to install Oracle 8.1.7Resolution:Homogenize the UNIX group to the one that has been compiled and linked into the Oracle executables: Determine the dba group that is embedded into the Oracle kernel by following the next step:  REF _Ref32144764 \r \h  \* MERGEFORMAT 1.2  REF _Ref32144764 \h  \* MERGEFORMAT Identify the Target dba Group . Use a UNIX editor to edit the file: /var/opt/oracle/oraInst.loc Make the group value match the dba group: inventory_loc=/export/disk2/oracle/oraInventory inst_group=xxxx If you for some reason did not encounter COG-00001 and were able to resolve any other errors, you must re-run the nhCheckOracleGroup script to double check your fixes: nhCheckOracleGroup Any and all COG errors must be resolved before proceeding with the upgrade. This rest of this section is only relevant if you received a COG-00001 error from Step  REF _Ref32147600 \r \h  \* MERGEFORMAT 1.1. Your UNIX system administrator will need to follow these steps before you can install eHealth 5.6. The goal is to homogenize the primary groups of the nhuser and oracle accounts (so that Oracle 9i will run properly) without impairing Oracle 8i and your eHealth 5.5 system. In this section, our examples presume that your $NH_USER (eHealth administrator account) is nhuser and that you installed the Oracle 8.1.7 software as UNIX user oracle. This is only done to simplify our documentation. Please make the necessary translations when viewing our examples. Identify the Target dba Group From Step 1.1, you must deduce the dba group that has been compiled and linked into the Oracle executables. In most cases, this will literally be dba since our eHealth 5.5 documentation recommended exactly that. We will use this group as the norm (whatever it is on your system) and change all others to match it. The dba group may appear on either the config.c line or the config.s line of the nhCheckOracleGroup output: :: ORACLE config.c group = xxx :: ORACLE config.s group = xxx Create Local Password and Group Entries If Needed If your are using NIS or NIS+, you should create local copies the passwd entries for nhuser and oracle as well as the corresponding groups. This will give you the ability to edit these entries locally for your eHealth system without affecting anything else in your enterprise. It also eliminates a runtime dependency that your eHealth system has on the NIS server. Please consult your UNIX system administration manuals on how to do this, but essentially, you will need to copy rows that look something like this: nhuser:.Lmf20EZqDetE:391:50:NetHealth User:/export/disk1/ehealth55:/bin/csh oracle:Sy15ghkucEriE:703:55:Eng Oracle:/export/disk2/oracle:/bin/csh and: dba::55:nhuser admin::50 and add them to your local files: /etc/passwd /etc/shadow (Solaris) /etc/group If your system has an /etc/shadow file, be careful to keep this in perfect synch with /etc/passwd or you may have trouble logging into the system (as any user, including root). Please consult your UNIX system administration manuals. Also, there is a remote chance that your UNIX configuration has been customized to ignore the password file, or to place it behind NIS in resolution order. You can validate that you still have the Homogenize the Groups You must now edit the local passwd entries so that the nhuser and oracle accounts contain the group ID corresponding to the dba group that you determined in Step  REF _Ref32144764 \r \h  \* MERGEFORMAT 1.2. The group IDs of both accounts must match the dba group. You will assuredly need to change the group ID for the nhuser account, but it is possible that you will need to alter both. In our example, the dba groups ID is 55. Note that in this passwd file excerpt, nhuser is group 50, not 55: nhuser:.Lmf20EZqDetE:391:50:NetHealth User:/export/disk1/ehealth55:/bin/csh oracle:Sy15ghkucEriE:703:55:Eng Oracle:/export/disk2/oracle:/bin/csh You would need to change nhusers group to 55 to match oracles group ID: nhuser:.Lmf20EZqDetE:391:55:NetHealth User:/export/disk1/ehealth55:/bin/csh oracle:Sy15ghkucEriE:703:55:Eng Oracle:/export/disk2/oracle:/bin/csh You can validate this step by issuing these commands as root and comparing the gid values. They must match exactly to each other and they must both match the dba group that you determined in Step  REF _Ref32140515 \r \h  \* MERGEFORMAT 0. su nhuser c id uid=1460(jkuefler) gid=55(dba) su oracle c id uid=703(oracle) gid=55(dba) Re-run the nhCheckOracleGroup Command Now you must re-run the nhCheckOracleGroup script to double check your fixes: nhCheckOracleGroup Any and all COG errors must be resolved before proceeding with the next two steps. Issue a Recursive Chgrp in NH_HOME This step should be coordinated with the next step ( REF _Ref32142102 \r \h  \* MERGEFORMAT 1.7  REF _Ref32142102 \h  \* MERGEFORMAT Restart eHealth) and with your downtime schedule. To ensure that you do not encounter file permission problems when running eHealth 5.5 (i.e. before you finish the upgrade process to eHealth 5.6), issue a recursive chgrp (change group) command from $NH_HOME: su root cd /opt/ehealth chgrp R dbagroupid . In our example, this would equate to: su root cd /opt/ehealth chgrp R 55 . Restart eHealth 5.5 and Oracle 8i Restarting the eHealth servers will cause brief downtime. Note: the next section requires you to stop and start eHealth and the database. If you are proceeding immediately to the next set of steps, you may defer this restart until then. On Solaris: su root /init.d/nethealth.sh stop /init.d/nethealth.sh start On HP-UX: su root /sbin/nethealth.sh stop /sbin/nethealth.sh start Validate that eHealth 5.5 is Working Properly Make Sure eHealth 5.5 is Polling In order to upgrade from eHealth 5.5 to eHealth 5.6, the 5.5 system must be functioning properly. The eHealth 5.5 system should be: Polling properly Void of ORA- and database errors on the eHealth Console Capable of running reports If any of these are not true, please resolve these issues before proceeding. Validate that you can Bring the System Down and Up During the upgrade process, we need to start and stop the eHealth servers and the Oracle 8i database several times. It is essential that you have no difficulties performing this operation. Restarting the eHealth servers will cause brief downtime. Even though this requires downtime, we feel that it is essential that you test this operation, before you make definitive plans for upgrading: On Solaris: su root /init.d/nethealth.sh stop /init.d/nethealth.sh start On HP-UX: su root /sbin/nethealth.sh stop /sbin/nethealth.sh start On Window NT40 and Win2K: nhServer stop nhStopDb If you encounter any ORA- or database errors to the terminal window (or command prompt), please research and resolve these before proceeding. Each time you make system configuration changes (including any Oracle configuration changes), you must perform this test again. Backup your eHealth 5.5 system. Please refer to procedure beginning on page 24 of your eHealth Database Management for Oracle book that came with your eHealth Suite 5.5 documentation. That section describes how to perform a Full Database Save. You should perform both an ascii and a binary save for safety. Always keep the saves in a different location from the database files and ehealth files. TODO If this is a NT system the most convenient way to be able to restore eHealth v5.5 is to use a tool like Norton Ghost to create images of all disks that you are using for the database / ehealth 5.5 and oracle 8i. Install eHealth 5.6 and bring system to Transition Mode. In transition mode eHealth v5.6 runs against the Oracle 8i database that you used in eHealth v5.5. The upgrade steps are to upgrade to eHealth v5.6, still running against Oracle 8i, and the upgrade Oracle to 9i to complete the upgrade. To upgrade to transition mode, if you are running an eHealth distributed cluster, perform the following steps. Install 5.6 nhUpgradeCluster activate If you are performing a parallel upgrade from v5.5 to v5.6 in a non-distributed environment, simply run the eHealth v5.6 Beta-2 installer. The 5.6 system will automatically be activated. Validate that Transition Mode is functioning properly. Check if the listener is running: On Unix: ps -ef | grep -i tnslsnr Sample output: rpattabh 29160 1 0 Jan 31 ? 0:01 /net/shovel/export/shovel/oracle/oracle.8.1.7/bin/tnslsnr LISTENER -inherit rpattabh 1507 28586 0 20:03:43 pts/19 0:00 grep -i tnslsnr On Windows H:\>ps -ef | grep -i tnslsnr Sample output: SYSTEM 664 41 0 20:02:00 CONIN$ 0:00 F:\oracle\ora817\BIN\TNSLSNR You should see a process like tnslistener running. The tns listener process should be running as user oracle on Unix and should be the oracle 8.1.7 listener process. Note the path and make sure this is the 8i listener. If you are running csh: source nethealthrc.csh If you are running ksh: . ./nethealthrc.sh (the first . followed by the space is part of the command.) Check if TWO_TASK is set. echo $TWO_TASK This variable should have a value of _${ORACLE_SID}, where is the name of the computer. If TWO_TASK is not set, please contact the Concord Beta Support team. If the listener is not running first login as user oracle and start it: Login as oracle Csh: source $NH_HOME/nethealthrc.sh Ksh: . $NH_HOME/nethealthrc.sh lsnrctl start Repeat step 1 and make sure the listener is now running Connect using the listener, you should see the following output indicating that the Oracle 9i version of sqlplus was used to connect to an 8i database: Login as nhuser sqlplus $NH_USER/$NH_USER SQL*Plus: Release 9.2.0.1.0 - Production on Thu Jan 30 23:09:37 2003 Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved. Connected to: Oracle8i Enterprise Edition Release 8.1.7.0.0 - Production With the Partitioning option JServer Release 8.1.7.0.0 - Production SQL> IMPORTANT: If you could not connect in #3 then your database is down. Run nhStartDb to start the database and repeat step #3. Do not proceed further unless #3 is successful and you see the above output. SOMETHINGize the system by upgrading Oracle 8i to Oracle 9i. To do the Oracle 8i to 9i upgrade do the following: login as root su root source nethealthrc from 5.6 NH_HOME Csh: source $NH_HOME/nethealthrc.sh Ksh: . $NH_HOME/nethealthrc.sh Run the following command: nhUpgradeOracleDb Once you have begun converting Oracle 8i to Oracle 9i, your system is vulnerable. A power outage or any unplanned abort of this procedure will leave your system in a broken state. Also, once the procedure has completed, there is no way to return to Oracle 8i without restoring to your system backup (produced in step  REF _Ref31533349 \r \h 3, on page  PAGEREF _Ref31533349 \h 9). In the event of a failure do the following: Failure on Unix system: Destroy the database cd to 5.5 NH_HOME su root NOTE: In the above command the is important dont forget to use it in suing to root source nethealthrc Csh: source $NH_HOME_OLD/nethealthrc.sh Ksh: . $NH_HOME_OLD/nethealthrc.sh Recreate the database from backup. nhLoadDb p saveDb.tdb Failure on NT system: Bring back the NT backup image of the v5.5 system that you created.    $%&'()*+,GHIJMNtuvִּֆִxjqUmHnHu&j>*B*UmHnHphuj{UmHnHujUmHnHumHnHu&j>*B*UmHnHphu mHnHu0JmHnHuj0JUmHnHu jU5CJOJQJ\^J6]/ !"*o3pL * % '  V'  V' $d0&d0N0P0kONOPijklmnopqɽɯɽכɽɍɽyɽ&j>*B*UmHnHphuj]UmHnHu&j>*B*UmHnHphujgUmHnHujUmHnHumHnHu mHnHu0JmHnHuj0JUmHnHu&j>*B*UmHnHphu,-./012345PQRSVWyz{ïޡÍj?UmHnHu&j>*B*UmHnHphujIUmHnHu&j>*B*UmHnHphu0JmHnHu mHnHuj0JUmHnHumHnHujUmHnHujSUmHnHu. !"OPQjklmnopqrɽɯɽכɽɍɽyɽ&j>*B*UmHnHphuj+UmHnHu&j>*B*UmHnHphuj5UmHnHujUmHnHumHnHu mHnHu0JmHnHuj0JUmHnHu&j>*B*UmHnHphu,+ , - F G H I J K L M N i j k l m n ïޡÍj UmHnHu&j >*B*UmHnHphuj UmHnHu&j >*B*UmHnHphu0JmHnHu mHnHuj0JUmHnHumHnHujUmHnHuj! UmHnHu.   # $ % ' ( ) * + , G H I J K L Z i ׾א׾n&jt >*B*UmHnHphuj UmHnHu&j~ >*B*UmHnHphuj UmHnHujUmHnHumHnHu0J6]mHnHu mHnHu0JmHnHuj0JUmHnHu&j >*B*UmHnHphu+      " # $ % & ]foTW-Wlo0356OҷCJ jCJ5CJOJQJ\^JCJOJQJ^J5CJOJQJ\^J6] jUj0JUmHnHuj UmHnHujUmHnHumHnHu0JmHnHu0J6]mHnHu mHnHu3' M N K L M h i 6Z:g & F & F & F3gC7Xd./W^ & FPWOpu"i Yoqno ^^OUVnopstu!i[d nFOoNXHPǽǷj5U\5\j5U\6]5CJOJQJ\^J 6CJ]5CJOJQJ\ CJOJQJ5CJOJQJ\^JCJOJQJ^Jjj5CJU\j5CJU\ 5CJ\8oMNZ LD$$Ifl0% X 64 la$If#$d%d&d'dNOPQvO& ' 3 C D 8`#$d%d&d'dNOPQ & FP$If$IfD$$Ifl0% X 64 la+,KLchz& ' 1 D I !!."v"w""""""##############$$>$Y$$$$$;%M%r%%%%5CJOJQJ\jV5U\j5U\5CJOJQJ\^J5CJOJQJ\^J 6CJ]5CJOJQJ\^J6]j5U\j`5U\5\=D K !!!*"+","."v"w"""""""#$d%d&d'dNOPQD$$Ifl0% X 64 la$If""A#$Z$$$$$q%r%%%%%%%%f&@`@D$$Ifl0% X 64 la & FP$If$If%%%&$&5&6&N&O&_&`&c&d&((]*o*x******,------- ..L.W.....]/c/e0f0~00000000y1{111111S222203i3jL5U\>* 6CJ]5CJOJQJ\^J5CJOJQJ\ 5CJ\CJOJQJ^J6]j5U\5\j5U\5CJOJQJ\^J?f&g&{'|'(((((**x******],^,,?---------^---..////P1Q1}1~1112S2T22220313)4:4Y4Z4j44^i3m3333344$4%4&4'4*4:4Z4j4444455 555555555556666%6&67>7H7I7J7K7r77778889=9>90:4:<<<<ײצצ5CJOJQJ\^J5CJOJQJ\^J 6CJ]j5U\jB5U\CJOJQJ^J5CJOJQJ\^Jj5U\5\j5U\>*6]<44444455d5f555I6J67%757K7L7r7|7777777^`@`@788888889 9%9>9?9A9o9p999:(:`:{:|:::::; & F^;;;;<<<<<<<<<===5=C=L=M===\>^>~>>??^<==5=K=L=b=f=>>>>>?@?R?@A^CmC I(JJJKLLLXMYMqMrMsMtMuMMMMMMMMMMO$OkO¬ mHnHujUj8U jU 5>*\5CJOJQJ^JaJ6] 56\]5CJOJQJ\^J5\5CJOJQJ\^J.?????????@@A AnAAAgBsBBBMCNCPCCCCC & F & F  & F  -DM CCCVDDDDDEE F F8FFFF#GiGGGGHHKHH & F 8^8 & F & F & F^ & FHH IRIIIII#J$J)JJJ5K6KjKkKyKKKKKLLLMM` & F & F ^ & FMMMMMNNsNNNNN OO$OiOjOkO8^8 & F & F & F 1h/ =!8"8#$%{DyK  _Toc32147732{DyK  _Toc32147732{DyK  _Toc32147733{DyK  _Toc32147733{DyK  _Toc32147734{DyK  _Toc32147734{DyK  _Toc32147735{DyK  _Toc32147735{DyK  _Toc32147736{DyK  _Toc32147736{DyK  _Toc32147737{DyK  _Toc32147737{DyK  _Toc32147738{DyK  _Toc32147738{DyK  _Toc32147739{DyK  _Toc32147739{DyK  _Toc32147740{DyK  _Toc32147740{DyK  _Toc32147741{DyK  _Toc32147741{DyK  _Toc32147742{DyK  _Toc32147742{DyK  _Toc32147743{DyK  _Toc32147743{DyK  _Toc32147744{DyK  _Toc32147744{DyK  _Toc32147745{DyK  _Toc32147745{DyK  _Toc32147746{DyK  _Toc32147746{DyK  _Ref32144764{DyK  _Ref32144764{DyK  _Ref32144764{DyK  _Ref32144764{DyK  _Ref32144764{DyK  _Ref32147600{DyK  _Ref32144764{DyK  _Ref32140515{DyK  _Ref32142102{DyK  _Ref32142102{DyK  _Ref31533349{DyK  _Ref31533349 i8@8 NormalCJ_HaJmH sH tH Z@Z Heading 1$ & F<@&5CJ KH OJQJ\^JaJ \@\ Heading 2$ & F<@& 56CJOJQJ\]^JaJV@V Heading 3$ & F<@&5CJOJQJ\^JaJJ@J Heading 4$ & F<@&5CJ\aJL@L Heading 5 & F<@&56CJ\]aJF@F Heading 6 & F<@&5CJ\aJ8@8 Heading 7 & F<@&>@> Heading 8 & F<@&6]L @L Heading 9 & F<@&CJOJQJ^JaJ<A@< Default Paragraph Font4P@4 Body Text 2$a$CJ`.U@. Hyperlink >*B*ph@ TOC 1&@& TOC 2 ^bS@2b Body Text Indent 3,%d'dOQ^<C@B< Body Text Indent ^@R@R@ Body Text Indent 2 ^&@& TOC 4 ^kK;9 !"*o3pL*%'MNKLMhi  6 Z    : g 3 g C 7Xd./WOpu"i YoqnoMNZ vO&'3CDK*+,.vwA Z q!r!!!!!!!!f"g"{#|#$$$$$&&x&&&&&&](^((?)))))))))))**++++P-Q-}-~---.S.T....0/1/)0:0Y0Z0j000000011d1f111I2J23%353K3L3r3|333333344444445 5%5>5?5A5o5p5556(6`6{6|66666777788888888899959C9L9M999\:^:~::;;;;;;;;;;<<= =n===g>s>>>M?N?P???????V@@@@@AA B B8BBBB#CiCCCCDDKDDD EREEEEE#F$F)FFF5G6GjGkGyGGGGGHHHIIIIIIJJsJJJJJ KK$KiKjKmK0000000000000000000000000 00'0'0'0'  00M0M0M0M 0M 0M0M0M 0M 0M 0M 0M 0M0M0M 0M 0M 0M 0M 0 00M0M0M 0M 00000000000000000000000000000000000000000000000M0M0M0M0M0M0M0M0M0M0M0M0M0M0M0M0M0M0M0M0M0M0M0M0M0M 0M 0M0M0M0M0M0M0M0M0M0M0M0M0M0M0M0M0M0M0M0M0M0M0M0M0M0M 0M 0M 0M0M0M0M0M0M0M0M0M0M0M0M0M0M0M0M0M0M0M0M 0MM0&$0&$0&$0&$0&$0&$0&$ 0MM0>&0>&0>&0>&0>&0>&0>&0>&0>&0>&0>&0>&0>&0>&0>&0>&0>&0>&0>& 0MM0-+0-+0-+0-+0-+0-+0-+0-+0-+0-+0-+0-+0-+0-+0-+0-+0-+0-+0-+0-+0-+0-+ 0MM0 00 00 00 00 00 00 0 0MM00000000000000000000000000 0MM030303030303030303030303030303  004 0440404 04 04 04040404 0440M60M60M60M60M60M60M60M60M60M60M60M60M60M60M60M60M60M60M60M60M60M60M60M60M6  009090909090909090909090909  00R<0R<0R<0R<0R< 0R< 0R<0R<0R<0R<0R<  00> 0> 0> 0-?> 0-?>0>0> 0> 0@> 0@>0>0> 0> 0> 0> 0> 0>0>0>0> 0> 0> 04C> 04C> 0> 0> 0> 0> 0>0>0>0>0>0>0>0>0> 0>0>  0000 0 0 0 0 0 0 0000000 0 0 00 0 0 0 0 000000 O%i3<kO(+,-./047:=A' WoD "f&-47;?CHMkO)1235689;<>?@BCDEkO* %'(*IuOjlmo.013RzPkmnp,GIJLk $'(*I"#%Uos+K 5"_"c"e,,,/$0&011112%2XIrItIIIIkK tX%tX%tX%tX%tX%tX%tX%tX%tX%tX%tX%tX%tX%tX%tX%t̕ttttttttttt%t _Ref32140515 _Ref32144764 _Toc32147734 _Toc32147735 _Toc32147736 _Toc32147737 _Toc32147738 _Ref32142102 _Toc32147739 _Toc32147740 _Toc32147741 _Toc32147742 _Ref31533349 _Toc32147743 _Toc32147744 _Toc32147745 _Toc32147746g"$$&+0f133A5p56^:^:<P?FmK $$$&+0133n556}:}:=?4GmK . 4 ] _ o  :DGJTWR\_blo%03!jpHPADchz|9=nuPS  ? Y z } ;!M!r!!####$$$$[%^% &&0&8&G&O&]&o&&&&&&&&&0'6'C'I'))Q*W*++++>,A,,, --f-i-----m.u.////*0,0-030:0=0C0K0M0P0T0W0Z0\0j0m0z0}000000001x1}12233%3'3-34353:3>3H3r3t3|3~333334444445555&57588888888889959=9C9K9o;t;;;<<s>>??????????V@^@@@@@@@@@@@3A>ALAOABBBB@>s>>%?+?????V@^@@@ BB:B$20]LM 2Q eHealth 5 Joe Kuefler Joe KueflerOh+'0t  0 < HT\dl eHealth 5 Hea Joe Kuefleroe oe Normalf Joe Kuefler1e Microsoft Word 9.0@| @@h#& />՜.+,D՜.+,8 hp  Concord]L  eHealth 5 Title 8@ _PID_HLINKSAZ1V _Toc321477461P _Toc321477451J _Toc321477441D _Toc321477431> _Toc3214774218 _Toc3214774112 _Toc321477406, _Toc321477396& _Toc321477386  _Toc321477376 _Toc321477366 _Toc321477356 _Toc321477346 _Toc321477336 _Toc32147732  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFHIJKLMNOPQSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~Root Entry Fu8&Data G.1TableReWordDocument"SummaryInformation(DocumentSummaryInformation8CompObjjObjectPoolu8&u8&  FMicrosoft Word Document MSWordDocWord.Document.89q